chore(brand): rebrand leftover Base naming to Cortex by echobt · Pull Request #196 · CortexLM/cortex

echobt · 2026-08-28T06:31:11Z

Summary

Product rebrand of this control-plane repo from leftover BASE / BaseIntelligence/base naming to Cortex (CortexLM/cortex), plus GitHub-standard community docs, AGENTS.md, dead-crate removal, and a documented CORTEX_* env alias. Branding + docs + hygiene only — not a protocol rewrite.

Why

The GitHub org/repo is already CortexLM/cortex, but README, workspace metadata, marketing frames, and agent docs still said BASE. Operators and contributors also lacked GitHub-standard community files. A previous investigation (bc-97cdbe65) never landed; this PR starts from current main and only does the verified-safe work.

What changed

Branding: README, AGENTS.md, CODEOWNERS, workspace Cargo.toml repository URL, LICENSE copyright holder, site-api arena source_url / repo refs, Prism HF banner URL, and a few doc H1s now say Cortex / CortexLM.
docs/NAMING.md: Cortex vs leftover base / BASE_* / domain tags / GHCR / host paths.
Config: crates/config still treats BASE_* as canonical. Matching CORTEX_* names are accepted aliases (CORTEX_ROLE ≡ BASE_ROLE, …). When both are set, BASE_* wins. Tests cover alias-only, BASE-wins, and CORTEX_CONFIG.
Dead code: removed unused workspace crate crates/design-rating (nothing imported design_rating). Did not drop the live Postgres design_rating table or design-db / design-store-pg accessors.
Community files: CONTRIBUTING.md, CODE_OF_CONDUCT.md (Contributor Covenant 2.1, contact via GitHub/CODEOWNERS), SECURITY.md (GitHub private vulnerability reporting — no fake inbox), SUPPORT.md, .github/ISSUE_TEMPLATE (bug + feature), PULL_REQUEST_TEMPLATE.md.
Docs accuracy: README now matches the live HTTP design/prism topology (no leftover Harbor/CVM miner path). Threat-model related-docs link no longer points at the removed AGENT_CHALLENGE.md.

How to test

cargo fmt --all -- --check
cargo test --workspace
cargo clippy --workspace --all-targets -- -D warnings
cargo deny check
cargo run -p xtask -- loc-cap
cargo run -p xtask -- consensus-lint
cargo run -p xtask -- spec-check
cargo run -p xtask -- design-check
cargo run -p xtask -- external-docs-check

Config-specific: cargo test -p config.

Test results (this agent)

Ran locally on this branch:

Gate	Result
`cargo fmt --all -- --check`	pass
`cargo test --workspace`	pass
`cargo clippy --workspace --all-targets -- -D warnings`	pass
`cargo run -p xtask -- loc-cap / consensus-lint / spec-check / design-check / external-docs-check`	pass
`cargo deny check` (local 0.20.2)	pre-existing: `chacha20 0.10.1` yanked via `rand 0.10.2` → `twox-hash`. Not introduced here; `Cargo.lock` only dropped the unused `design-rating` package. Same lock pin is on `main`.

GitHub Actions on this PR (33148194339) failed in ~4s with empty job steps (no checkout/fmt/test). That is an Actions start/permission failure, not a compile failure. Latest main CI that actually ran steps was green (32550193889).

Risk notes

Low operational risk: no compose/image pin, no BASE_* reader rename, no domain-tag change, no on-chain name change.
Frozen specs: H1 title on BUNDLE_SPEC.md / crate-table row on DESIGN_CHALLENGE.md only. xtask pin strings for scoring/consensus are unchanged.
Marketing site source_url now points at https://github.com/CortexLM/cortex. Banner raw URL follows the same repo. GHCR package path is not moved.
Public miner-doc repos (BaseIntelligence/design-challenge, BaseIntelligence/prism) and Hub publish defaults are left as live URLs until those properties actually move.

Identifiers left as Base / `BASE_*` (intentional)

Identifier	Why it stays
All `BASE_*` env vars (compose, droplets, CVM `app-compose.json`)	Measured / live; renaming forks miner RTMR3 pin continuity
Crypto domain tags (`base-bundle-v1`, `base-rawweight-v1`, `base-sr25519-v1`, design `base-design-*-v1`, …)	Changing them makes old signatures unverifiable
Host paths (`/opt/base`, `/run/base`, `/var/lib/base`, `/etc/base`, systemd `base-*-seal`)	Live droplet layout
Compose project `COMPOSE_PROJECT_NAME=base`, sandbox prefix `base-design-`	Deployed + design-check pin
GHCR `ghcr.io/baseintelligence/base/<suffix>`	Existing digest pins / package path
Host nicknames `base-staging`, `base-prod`	Terraform / operator inventory
Public miner repos `BaseIntelligence/{design-challenge,prism}`	Separate GitHub properties; URLs still live
HF/GitHub top-model defaults `BaseIntelligence/top-prism-architecture`, `BaseIntelligence/prism` `top-model/`	Compose publish targets
Gateway DNS `chain.joinbase.ai`	Operator DNS, not a docs rename
Postgres table `design_rating`	Live design scoring path
`docs/evidence/`, `docs/spikes/` historical BASE mentions	Non-normative; do not rewrite in cleanup

See docs/NAMING.md and AGENTS.md.

greptile-apps · 2026-08-28T06:44:19Z

Greptile Summary

This change completes Cortex branding and community documentation updates, adds CORTEX_* configuration aliases while preserving BASE_* precedence, and removes an unused rating package. The bug-report form contains a broken relative link to the security policy: it resolves to a nonexistent .github/SECURITY.md instead of the repository-root SECURITY.md.

Merge safety: address the issue-form link before merging so reporters can reach the security-reporting instructions.

Confidence Score: 4/5

The change needs a small documentation-link correction before it is ready to merge.

The relative-path behavior was directly exercised against the committed template and compared with the corrected path, confirming one isolated issue.

Files Needing Attention: .github/ISSUE_TEMPLATE/bug.yml line 9 should link to the root SECURITY.md file.

T-Rex Logs

What T-Rex did

T-Rex produced two finding-comment proofs for the posted P2 finding and attached the Markdown link resolution verifier source and its outputs.
A general-contract-validation-proof was added, showing how root policy path resolution was validated and identifying the fault location at .github/ISSUE_TEMPLATE/bug.yml:9.
Artifacts from both proofs were prepared and uploaded for reviewer inspection, including the verifier source, captured outputs, broken link resolution results, and root policy path comparisons, plus the general contract validation sources and logs.

_{Ran code and verified through T-Rex}

Comments Outside Diff (1)

General comment

Bug-report security-policy link targets a nonexistent file
- Bug
  - The Markdown link ../SECURITY.md in the bug issue template is evaluated relative to .github/ISSUE_TEMPLATE/, so it points to .github/SECURITY.md. That target is absent even though the repository policy is present at the root as SECURITY.md.
- Cause
  - The relative path climbs one directory from .github/ISSUE_TEMPLATE/ to .github/ rather than two directories to the repository root.
- Fix
  - Change the link target on .github/ISSUE_TEMPLATE/bug.yml:9 to ../../SECURITY.md (or use a repository-root-anchored GitHub URL).
_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "chore(brand): rebrand leftover base nami..." | Re-trigger Greptile}

greptile-apps · 2026-08-28T06:44:22Z

+    attributes:
+      value: |
+        Use this for defects in **this** repo (gateway, validator, challenges, deploy).
+        Security issues: do **not** file here — see [SECURITY.md](../SECURITY.md).


Bug-report security-policy link targets a nonexistent file

../SECURITY.md resolves relative to .github/ISSUE_TEMPLATE/, so the form links to .github/SECURITY.md, which does not exist. The repository policy is at the root as SECURITY.md, leaving reporters unable to reach the security-reporting instructions from this form. Change the target to ../../SECURITY.md or use a repository-root URL.

Artifacts

Markdown link resolution verifier source

Review-authored Python verifier that reads the template link and resolves it from the template directory, providing reproducible validation.

Captured Markdown link resolution verifier source

Command capture showing the exact review-authored verifier source that was used for the resolution checks.

Broken Markdown link resolution output

Executed verifier output for the committed `../SECURITY.md` link; it resolves to absent `.github/SECURITY.md`, confirming the failure.

Root security policy path comparison output

Executed same-scope comparison with `../../SECURITY.md`; it resolves to the existing root `SECURITY.md`, demonstrating the required path depth.

_{Ran code and verified through T-Rex}

chore(brand): rebrand leftover base naming to cortex

be0df1e

echobt marked this pull request as ready for review August 28, 2026 06:38

greptile-apps Bot reviewed Aug 28, 2026

View reviewed changes

Navigation Menu

Uh oh!

chore(brand): rebrand leftover Base naming to Cortex - #196

chore(brand): rebrand leftover Base naming to Cortex#196
echobt wants to merge 1 commit into
mainfrom
cursor/cortex-rebrand-873f

echobt commented Aug 28, 2026 •

edited by cursor Bot

Loading

Uh oh!

greptile-apps Bot commented Aug 28, 2026 •

edited

Loading

T-Rex Logs

Comments Outside Diff (1)

Uh oh!

greptile-apps Bot Aug 28, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

echobt commented Aug 28, 2026 • edited by cursor Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Why

What changed

How to test

Test results (this agent)

Risk notes

Identifiers left as Base / BASE_* (intentional)

Uh oh!

greptile-apps Bot commented Aug 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Greptile Summary

Confidence Score: 4/5

T-Rex Logs

Comments Outside Diff (1)

Uh oh!

greptile-apps Bot Aug 28, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

echobt commented Aug 28, 2026 •

edited by cursor Bot

Loading

Identifiers left as Base / `BASE_*` (intentional)

greptile-apps Bot commented Aug 28, 2026 •

edited

Loading